Application processing method and apparatus and storage medium

ABSTRACT

An application processing method and apparatus, a storage medium, and a computer device are provided. The method includes: displaying a first child application page of a first child application; and acquiring, by using the first child application, a second child application identifier corresponding to a second child application to be jumped to. The first child application is run by a parent application. The method also includes: the parent application running the second child application when a jump is made from the first child application to the second child application; transferring page data corresponding to the second child application identifier to the second child application; and generating, according to the page data, a second child application page over the first child application page, and displaying the second child application page.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation application of PCT Patent ApplicationNo. PCT/CN2018/085527, filed on May 4, 2018, which claims priority toChinese Patent Application No. 201710524874.0, entitled “APPLICATIONPROCESSING METHOD AND APPARATUS, STORAGE MEDIUM, AND COMPUTER DEVICE”filed on Jun. 30, 2017, the entire contents of both of which areincorporated herein by reference.

FIELD OF TECHNOLOGY

The present application relates to the field of computer technologies,and in particular, to an application processing method and apparatus anda storage medium.

BACKGROUND OF THE DISCLOSURE

An application is a code instruction sequence or is a symbolizedinstruction sequence or a symbolized statement sequence that may beautomatically converted into a code instruction sequence, where the codeinstruction sequence may be executed by a terminal such as a computerhaving an information processing capability to obtain a result.Currently, a user may install various applications such as aphotographing application, a social networking application or an emailapplication on a terminal, so as to use these applications installed onthe terminal to implement various functions such as a photographingfunction, a social networking function or an email management function.

SUMMARY

Embodiments of the present application provide an application processingmethod and apparatus and a storage medium.

An application processing method is applied to a terminal. The methodincludes: displaying a first child application page of a first childapplication; and acquiring, by using the first child application, asecond child application identifier corresponding to a second childapplication to be jumped to. The first child application is run by aparent application. The method also includes: running, by the parentapplication, the second child application when a jump is made from thefirst child application to the second child application; transferringpage data corresponding to the second child application identifier tothe second child application; and generating, according to the pagedata, a second child application page over the first child applicationpage, and displaying the second child application page.

An application processing apparatus includes a processor and a memory,the memory storing computer readable instructions, and the instructionsenabling the processor to: display a first child application page of afirst child application; and acquire, by using the first childapplication, a second child application identifier corresponding to asecond child application to be jumped to. The first child application isrun by a parent application. The processor is also enabled to: run, bythe parent application, the second child application when a jump is madefrom the first child application to the second child application;transfer page data corresponding to the second child applicationidentifier to the second child application; and generate, according tothe page data, a second child application page over the first childapplication page, and displaying the second child application page.

A non-transitory computer readable storage medium stores computerreadable instructions, when being executed by a processor, the computerreadable instructions enabling the processor to perform the followingsteps: displaying a first child application page of a first childapplication; and acquiring, by using the first child application, asecond child application identifier corresponding to a second childapplication to be jumped to. The first child application is run by aparent application. The computer readable instructions also cause theprocessor to perform: running, by the parent application, the secondchild application when a jump is made from the first child applicationto the second child application; transferring page data corresponding tothe second child application identifier to the second child application;and generating, according to the page data, a second child applicationpage over the first child application page, and displaying the secondchild application page.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of an application environment of an applicationprocessing system according to an embodiment of the present application;

FIG. 2 is a schematic flowchart of an application processing methodaccording to an embodiment of the present application;

FIG. 3 is a schematic diagram of relationships among an operating system(OS), a parent application, a child application, and a child applicationpage according to an embodiment of the present application;

FIG. 4 is a schematic diagram of returning to a child applicationaccording to an embodiment of the present application;

FIG. 5 is a schematic diagram of closing a child application accordingto an embodiment of the present application;

FIG. 6 is a schematic diagram of jumping to a child applicationaccording to an embodiment of the present application;

FIG. 7 is a schematic flowchart of an application processing methodaccording to another embodiment of the present application;

FIG. 8 is a structural block diagram of an application processingapparatus according to an embodiment of the present application;

FIG. 9 is a structural modular diagram of a parent application accordingto an embodiment of the present application;

FIG. 10 is a structural modular diagram of a parent applicationaccording to another embodiment of the present application; and

FIG. 11 is an internal structural diagram of a computer device accordingto an embodiment of the present application.

DESCRIPTION OF EMBODIMENTS

To make the objectives, the technical solutions, and the advantages ofthe present application clearer, the following further describes thepresent application in detail with reference to the accompanyingdrawings and the embodiments. It should be understood that the specificembodiments described herein are only used to describe the presentapplication instead of limiting the present application.

FIG. 1 is a diagram of an application environment of an applicationprocessing system according to an embodiment of the present application.Referring to FIG. 1, the application processing system includes aterminal 110 and a server 120. The terminal 110 and the server 120 areconnected via a network. An OS runs on the terminal 110. A parentapplication runs on the OS. The terminal 110 implements an applicationprocessing method, so as to implement a child application jump by usingthe parent application. A jump, as used herein, may refer to a redirectevent (or a switch event) from one child application page to anotherchild application page within the parent application, a redirect eventfrom a parent application page to a child application page, or aredirect event from a child application page to the parent applicationpage. The redirect/jump event may be triggered in response to a userinstruction and/or when certain conditions are satisfied. The terminal110 may specifically create a child application logic layer unit and acorresponding child application view layer unit by using the parentapplication. A child application view layer processing unit may beconfigured to generate a child application page. The server 120 maystore data required to generate the child application page, for example,page data corresponding to a child application identifier.

FIG. 2 is a schematic flowchart of an application processing methodaccording to an embodiment of the present application. This embodimentis mainly described by using an example in which the method is appliedto the terminal 110 in FIG. 1. Referring to FIG. 2, the applicationprocessing method specifically includes the following steps:

S202: Display a child application page (or a first child applicationpage) of a child application (or a first child application), where thechild application is run by a parent application.

Specifically, an OS runs on a terminal, and the parent application runson the OS. The OS is a computer program for managing and controllinghardware and software resources of the terminal, and is fundamentalsystem software that directly runs on a bare-metal terminal. The supportof the OS is required to run applications. The OS may be a desktop OSsuch as Windows OS, Linux OS or Mac OS (Apple's desktop OS), or may be amobile OS such as iOS (Apple's mobile terminal OS) or Android OS.

The parent application is a native application. The native applicationis an application that can be directly run on the OS. The parentapplication may be a social networking application, an emailapplication, a game application or the like. The social networkingapplication includes an instant messaging application, a social networkservice (SNS) application, a live broadcast application or the like. Theparent application may be specifically the WeChat program (WeChat).

FIG. 3 is a schematic diagram of relationships among the OS, the parentapplication, the child application, and the child application pageaccording to an embodiment of the present application. Referring to FIG.3, an OS 301 runs on a terminal, and a parent application 302 runs onthe OS 301. The parent application 302 provides an environment forrunning of the child application. The terminal may create, according toa program package of the child application, a child application logiclayer unit 304 and a corresponding child application view layer unit 305for implementing the child application. The child application logiclayer unit 304 may be configured to execute page logic code in theprogram package. The child application view layer unit 305 may beconfigured to execute page structure code in the program package, andmay further execute page style code in the program package. The pagelogic code, the page structure code, and the page style code in theprogram package may be generally referred to as page code.

In an embodiment, the terminal creates the child application logic layerunit 304 and the corresponding child application view layer unit 305 byusing the parent application when the child application is to be run inan environment provided by the parent application. The terminal may thenuse the parent application 302 to acquire the program packagecorresponding to the child application and page data corresponding tothe child application, so as to acquire the page code from the programpackage. The page code may include the page logic code, the pagestructure code, and the page style code.

The terminal may then execute the page structure code by using the childapplication view layer unit 305, select, from a common component libraryaccording to an identifier of a common component defined in the executedpage structure code, the common component corresponding to theidentifier, acquire default component style data built in the commoncomponent, organize the common component according to the defaultcomponent style data, apply the page data to the common component andperform rendering, and form and present the child application page, soas to display the child application page of the child application run bythe parent application.

The page structure code is code for defining page components. The pagestructure code may include the identifier of the common componentincluded on the page. The page style code is code for defining a pagestyle. The page logic code is code for defining process logic of acorresponding child application page. The common component is acomponent shared by pages of different child applications, has a visualform, and is a component of the child application page. The commoncomponent has a unique identifier, and the identifier may be a name ofthe common component.

S204: Acquire, by using the child application, a child applicationidentifier (or a second child application identifier) corresponding to achild application (or a second child application) to be jumped to. Theparent application can run the second child application when a jump ismade from the first child application to the second child application.

The child application identifier is used for uniquely identifying onechild application. After each child application is run in the parentapplication, the parent application may assign a child applicationidentifier (for example, an APP ID) for uniquely identifying each childapplication to each child application. Each child application may beturned on by using an identifier of the child application. For example,after each child application (for example, a bicycle sharingapplication, and a coupon application) is run in WeChat, WeChat assignsan APP ID to the child application such as a bicycle sharing functionand a coupon function to uniquely recognize the child application suchas the bicycle sharing function or the coupon function. A bicyclesharing child application acquires an APP ID of a coupon childapplication to turn on the coupon child application when it is necessaryto jump from the bicycle sharing child application to the coupon childapplication. The child application identifier may be a character stringincluding characters of at least one type of digit, letter, and symbol,for example, X123456789.

Specifically, the terminal may monitor or listen to, by using a childapplication (that is, the first child application) of a currentlydisplayed child application page (that is, the first child applicationpage), an event triggered in the currently displayed child applicationpage. The event is used for triggering a jump from the child applicationto which the currently displayed child application page belongs toanother child application (that is, the second child application). Theevent may be a trigger operation on a jump portal. The jump portal maybe specifically an icon, a link, a virtual button or the like. The eventmay be alternatively an event triggered after a specified event occurs.For example, the event is an event, triggered after a payment method isselected during a payment, of jumping to a child applicationcorresponding to the selected payment method.

The child application identifier (that is, the second child applicationidentifier) corresponding to the child application to be jumped to isacquired when the terminal detects or hears, by using the childapplication to which the currently displayed child application pagebelongs, that an event of jumping from the child application to whichthe currently displayed child application page belongs to another childapplication is triggered.

In an embodiment, the child application identifier corresponding to thechild application to be jumped to may be carried in the jump portal. Thechild application to which the currently displayed child applicationpage belongs may extract, after detecting the trigger operation on thejump portal, the child application identifier encapsulated in the jumpportal. The child application identifier corresponding to the childapplication to be jumped to may be a child application identifier found,according to the time of detecting or hearing the event, by the childapplication to which the currently displayed child application pagebelongs.

S206: Transfer page data corresponding to the child applicationidentifier (or the second child application identifier) to the childapplication (or the second child application) that corresponds to thechild application identifier and is run by the parent application.

The page data is data to be presented on the child application page. Thepage data may be text data, voice data, video data, image data or thelike. The page data may be dynamic data or may be static data. Thedynamic data may be continuously changing data or may be periodicallychanging data.

In an embodiment, the page data corresponding to the child applicationidentifier may be page data included on a page generally chosen for thechild application corresponding to the child application identifier. Thegenerally chosen page is, for example, a front page of the childapplication. The front page of the child application is a page directlydisplayed after the child application is loaded. The page datacorresponding to the child application identifier may be alternativelypage data that belongs to a specific page of the child applicationcorresponding to the child application identifier, for example, pagedata on a page having email content in an email application or page dataon a page having weather information in a weather application.

Specifically, the terminal may acquire, by using the parent application,a child application global logic file corresponding to the childapplication to be jumped to, create the child application logic layerunit according to the child application global logic file, then acquirea child application global configuration file corresponding to the childapplication identifier, acquire a child application page configurationfile specified in the child application global configuration file, andcreate the child application view layer unit according to the childapplication page configuration file.

Further, the child application logic layer unit initiates a page dataacquisition request for acquiring page data corresponding to the childapplication to be jumped to. The parent application then acquires,according to the page data acquisition request, the page datacorresponding to the child application to be jumped to from a servercorresponding to the parent application or a server corresponding to thechild application. After acquiring the page data, the parent applicationtransfers the acquired page data to the child application view layerunit.

The terminal may invoke a child application launch interface provided bythe parent application to create the child application logic layer unitand the child application view layer unit corresponding to the childapplication to be jumped to or may switch to a parent application pageused for triggering a child application jump, so as to trigger creationof the child application logic layer unit and the child application viewlayer unit corresponding to the child application to be jumped to. Thechild application launch interface may be specifically launch JSAPI orthe like.

In an embodiment, the terminal may further send, by using the parentapplication, the page data acquisition request to the servercorresponding to the parent application, so that the servercorresponding to the parent application acquires, from the servercorresponding to the child application to be jumped to, the page datacorresponding to the child application to be jumped to.

In an embodiment, by using child applications, the terminal acquires thechild application identifier corresponding to the child application tobe jumped to, and acquires a child application identifier correspondingto the currently displayed child application page. The terminal thensends the two child application identifiers and a child applicationjumping relationship (e.g., a redirect event that includes anapplication before the jump and another application after the jump) tothe server. The server detects whether the received child applicationjumping relationship is allowed. Default page data is returned if thereceived child application jumping relationship is forbidden.

Herein, the parent application (for example, WeChat) or the server (forexample, a WeChat server) corresponding to the parent application mayexamine a child application list (the list includes child applicationsto which a jump from a child application A is permitted) for a jump fromthe child application A and a child application list (the list includeschild applications to which a jump from a child application B ispermitted) for a jump from the child application B when it is necessaryto jump from the child application A to the child application B (thatis, the jumping relationship is A→B). The jumping relationship A→B isvalid if a jump from the child application A to the child application Bis permitted and a jump from the child application B to the childapplication A is permitted. Otherwise, the jumping relationship A→B isforbidden. That is, a jump from the child application A to the childapplication B is not allowed.

It is then detected whether the child application to be jumped to iseffective if the received child application jumping relationship isallowed. The page data corresponding to the child application to bejumped to is returned if the child application to be jumped to iseffective. The default page data is returned.

For example, the parent application sends a jumping relationship ofjumping from A to B and child application identifiers of A and B to theserver if it is intended to jump from the child application A running inthe parent application to the child application B. The server detectswhether a jump from A to B is allowed. The default page data is returnedif the jump is not allowed. It is then detected whether B is effectiveif the jump is allowed. Page data corresponding to B is returned if B iseffective. The default page data is returned if B is ineffective.

In an embodiment, the page data corresponding to the child applicationidentifier includes data transferred by the child applicationcorresponding to the currently displayed child application page. Thedata transferred by the child application corresponding to the currentlydisplayed child application page may be a page path and a page parameterof the child application to be jumped to or may be data that can befilled on the child application page of the child application to bejumped to.

In an embodiment, after acquiring, by using the child application, thechild application identifier corresponding to the child application tobe jumped to, the terminal may detect whether a code packagecorresponding to the child application identifier is locally stored.Page data on a default loaded page is acquired if a locally stored codepackage corresponding to the child application identifier is notdetected, the default loaded page is generated and displayed over thedisplayed child application page, and a code package is downloaded fromthe server corresponding to the child application identifier, and codein the code package is executed to run the corresponding childapplication.

S208: Generate, according to the page data, a child application page(that is, a second child application page) displayed over the displayedchild application page (that is, the first child application page).

Specifically, the terminal may execute, by using the child applicationview layer unit corresponding to the child application identifier, thepage structure code corresponding to the child application identifier,select, from a common component library according to an identifier of acommon component defined in the executed page structure code, the commoncomponent corresponding to the identifier, acquire default componentstyle data built in the common component, organize the common componentaccording to the default component style data, apply the page data tothe common component and perform rendering, and generate the childapplication page displayed over the displayed child application page.

In an embodiment, the terminal may display, over the displayed childapplication page by using the parent application, the child applicationpage generated by the child application view layer unit corresponding tothe child application identifier according to the page data.

In an embodiment, the child application page generated by the childapplication view layer unit corresponding to the child applicationidentifier according to the page data may be alternatively automaticallydisplayed over the displayed child application page.

In the foregoing application processing method, a parent applicationruns on the OS, a child application may be run by the parentapplication, and a child application page that belongs to the childapplication is displayed. The parent application only needs to acquire,by using the child application, a child application identifiercorresponding to a child application to be jumped to before the parentapplication can transfer page data corresponding to the childapplication identifier to the child application that corresponds to thechild application identifier and is run by the parent application whenit is necessary to make a child application jump, and the childapplication corresponding to the child application identifier may thengenerate, according to the page data, a child application page displayedover the displayed child application page, so as to automaticallyimplement the child application jump. The time required to exit acurrently used application and then start an intended application to bejumped to is avoided, and application use efficiency is improved.

By using the foregoing technical solution, child applications mayimplement complementary functions. That is, the child applications mayconstitute a collaborative environment. For example, some childapplications focus on platform functions (for example, a job-searchplatform function) and specialized functions (for example, a couponfunction) to provide services to other child applications. Some otherchild applications focus on business functions (for example, a bicyclesharing function). In this way, child applications can be developedfaster at lower costs, and the child applications become more intensiveand extensive (for example, the child applications implementcomplementary functions to grow more powerful, and therefore moreintensive functions are fulfilled; and with the foregoing jump function,a jump may be made from one child application to other childapplications, so that more extensive functions are fulfilled). Forexample, WeChat (the parent application) has a coupon management childapplication that provides a function of managing membership cards. Ajump may be made from other child applications that need to use amembership card to a coupon application (child application) in theforegoing child application jump manner, so as to implement membershipcard management such as membership registration and score management. Inthis way, other child applications can conveniently integrate amembership card function without expending corresponding labor andresources.

In an embodiment, after S204, the application processing method furtherincludes: acquiring a jump path used for recording one or more existingchild application jumping relationships; moving the acquired childapplication identifier to the end of the jump path when the acquiredchild application identifier exists in the jump path; and adding theacquired child application identifier to the end of the jump path whenthe acquired child application identifier does not exist in the jumppath.

The jump path includes child application identifiers arranged in a childapplication jump sequence, and records the child application jumpingrelationship. In other words, the jump path including one or more childapplication identifiers arranged in a specific sequence based on one ormore previous jumps. For example, the jump path in the child applicationjumping relationship recording “jumping from the child application A tothe child application B and then to a child application C” is: A→B→C.

Specifically, the terminal may acquire, by using the parent application,the jump path used for recording one or more existing/historical childapplication jumping relationships, traverse child applicationidentifiers in the acquired jump path, and compare a traversed-to childapplication identifier with the acquired child application identifier.The traversed-to child application identifier is moved to the end of thejump path when the parent application determines that the traversed-tochild application identifier is the same as the acquired childapplication identifier. The acquired child application identifier isdirectly added to the end of the jump path when the parent applicationdetermines that no traversed-to child application identifier is the sameas the acquired child application identifier.

For example, it is assumed that the jump path acquired by the terminalby using the parent application is “A→B→C”. If it is currently intendedto jump from a child application corresponding to C to a childapplication corresponding to B, in this case, B exists in “A→B→C”, B ismoved to the end of “A→B→C” to obtain “A→C→B”. If it is currentlyintended to jump from the child application corresponding to C to achild application corresponding to D, in this case, D does not exist in“A→B→C”, D is directly added to the end of “A→B→C” to obtain “A→B→C→D”.

In an embodiment, the terminal may detect, by using the parentapplication, whether the child application with the acquired childapplication identifier is currently run in an environment provided bythe parent application when the acquired child application identifierexists in the jump path; and, search for a page path that exists whenthe child application with the acquired child application identifier isrun if the child application is currently run. It is not necessary tofirst close the child application if the page path that exists when thechild application is run is not consistent with a page path of a page ofa currently intended child application to be jumped to, and the page ofthe currently intended child application to be jumped to may begenerated by invoking a reload interface. The reload interface may bespecifically Relaunch JSAPI or the like.

In some embodiments, the child application jumping relationship isrecorded, so as to return to accessed child applications sequentiallyduring a child application jump in an environment provided by the parentapplication.

In an embodiment, the application processing method further includes:acquiring a return instruction by using a child application to which acurrently displayed child application page belongs (i.e., the returninstruction is received while displaying the child application page oris from the child application); in response to the return instruction,determining the child application identifier corresponding to thecurrently displayed child application page; searching the jump path fora child application identifier that is adjacent to the determined childapplication identifier and is located before the determined childapplication identifier; and returning to the child application pagecorresponding to the found child application identifier.

The return instruction is an instruction used for returning to aprevious child application (that is, a third child application, wherethe third child application may be the same as or different from thefirst child application). The return instruction may be a passivelytriggered instruction or an actively triggered instruction. Thepassively triggered instruction is a return instruction passivelytriggered after the child application to which the currently displayedchild application page belongs detects a trigger event. The activelytriggered instruction is a return instruction actively triggered by thechild application to which the currently displayed child applicationpage belongs.

In an embodiment, the terminal may monitor or listen to, by using thechild application to which the currently displayed child applicationpage belongs, an event triggered in the currently displayed childapplication page. The event is used for triggering a return from thechild application to which the currently displayed child applicationpage belongs to a previously started child application (that is, thethird child application). The event may be a trigger operation on anoperation portal such as an icon or a virtual button. The triggeroperation may be a touch operation, a click operation (for example, aclick operation on the control 400 in FIG. 4) or a swipe operation (forexample, a left-to-right swipe operation on the page shown in FIG. 4)and the like.

In an embodiment, the terminal may automatically trigger a returninstruction after the child application to which the currently displayedchild application page belongs finishes performing a specific operation.For example, the child application to which the currently displayedchild application page belongs is a payment child application. In thiscase, after the payment child application finishes a payment, a returninstruction for returning to a previous child application isautomatically triggered. The return instruction may be automaticallytriggered by invoking a return interface provided by the parentapplication. The return interface may be specifically Back JSAPI or thelike.

In an example, when making a child application return according to areturn instruction, the terminal may acquire data that needs to betransferred by a current child application from which the return is madeto the child application to be returned to, and then transfer theacquired data to the child application to be returned to. Generally,data is transferred in all returns triggered by invoking the returninterface provided by the parent application.

Specifically, after acquiring the return instruction by using the childapplication to which the currently displayed child application pagebelongs, the terminal determines, in response to the return instruction,the child application identifier corresponding to the currentlydisplayed child application page, then searches the jump path for thechild application identifier that is adjacent to the determined childapplication identifier and is located before the determined childapplication identifier, and returns to the child application pagecorresponding to the found child application identifier.

In an embodiment, the returning to the child application pagecorresponding to the found child application identifier includes:returning to a child application page displayed during a jump by thechild application corresponding to the found child applicationidentifier when the child application corresponding to the found childapplication identifier is run by the parent application in a backgroundstate (e.g., most recent jump recorded in the jump path is from childapplication A to child application B, and when that jump occurred, childapplication A was left off at page A and made to run in the background.The user terminal is currently displaying page B of child application B,and when a return instruction is received, the user terminal may returnto page A of child application A); and returning to a default childapplication page corresponding to the found child application identifierwhen the child application corresponding to the found child applicationidentifier has finished running.

When being run by the parent application in a background state, thechild application is run by the parent application but is not displayedon a page by using a view layer. A foreground state is a conceptcorresponding to the background state. When being run by the parentapplication in a foreground state, the child application is run by theparent application and is displayed on a page by using the view layer.After a jump is made from one child application to another childapplication, the child application from which the jump is made is notclosed but continues to be run by the parent application in a backgroundstate until the child application running in a background state ismanually closed or is closed by the parent application because runningtimes out. For example, the child application is closed when being runin the background over ten minutes.

Specifically, after determining, by using the parent application, thechild application to be returned to, the terminal may search a childapplication running management list for the child application identifiercorresponding to the child application to be returned to. If the childapplication identifier corresponding to the child application to bereturned to is found in the child application running management list,it indicates that the child application to be returned to is run by theparent application in a background state. The terminal may switch, byusing the parent application, the child application to be returned to aforeground state for running, and display a child application pagedisplayed by the child application to be returned to during a jump.

If the child application identifier corresponding to the childapplication to be returned to is not found in the child applicationrunning management list, it indicates that the child application to bereturned to has finished running. The terminal may acquire, by using theparent application, page data of the default child application pagecorresponding to the child application to be returned to, so as todisplay the default child application page corresponding to the childapplication to be returned to. For example, the parent applicationrelaunch (or start) the child application and display a front page orthe like of the child application.

In some embodiments, the child application may be switched to theforeground for running to swiftly return to a page displayed by thechild application to be returned to during the jump when the childapplication to be returned to is still run in the background, so that auser may continue to operate on the page, thereby improving applicationconvenience. In addition, the default child application page of thechild application to be returned to is directly returned to in theparent application when the child application to be returned to hasfinished running, so that the time for manual switching is avoided, andapplication use efficiency is improved.

In the foregoing embodiments, a processing manner of jumping from achild application and then returning to the child application isprovided, so that a return may be directly made in the parentapplication when it is intended to return to a used child application,the time required to exit a currently used application and then start anintended application to be returned to is avoided, and application useefficiency is improved.

FIG. 4 is a schematic diagram of returning to a child applicationaccording to an embodiment. Referring to FIG. 4, the schematic diagramincludes a return operation portal 400, a currently displayed childapplication page 401, a child application page 402 displayed by thechild application to be returned to during a jump, and a default childapplication page 403 of the child application to be returned to. Thechild application page 402 displayed by the child application to bereturned to during a jump is displayed over the currently displayedchild application page 401 when the terminal determines, by using theparent application after detecting the trigger operation on the returnoperation portal 400, that the child application to be returned to isrun by the parent application in a background state. The default childapplication page 403 of the child application to be returned to isdisplayed over the currently displayed child application page 401 whenthe terminal determines, by using the parent application, that the childapplication to be returned to has finished running.

In an embodiment, the child application includes a native plug-in childapplication, and the moving the acquired child application identifier tothe end of the jump path when the acquired child application identifierexists in the jump path includes: determining a consecutive nativeplug-in child application identifier (i.e., determining a native plug-inchild application identifier, and such chain may include one or moreconsecutively arranged native plug-in child application identifiers)that is adjacent to the acquired child application identifier in thejump path and is located after the acquired child application identifierwhen the acquired child application identifier exists in the jump path;and moving the acquired child application identifier to the end of thejump path, and deleting the consecutive native plug-in child applicationidentifier (i.e., all consecutive native plug-in child applicationidentifier in the chain) in the jump path.

The native plug-in child application is a child application that isdeveloped by a developer of the parent application and is configured toimplement a plug-in function such as a “Nearby Portal” child applicationor a “Scan QR Code” child application of the parent application. Thenative plug-in child application and the parent application may beconsidered as a whole when the native plug-in child application is runin the parent application. The native plug-in child application and anintended child application to be jumped to may be considered as a wholewhen a jump is made from a child application to the native plug-in childapplication.

Specifically, the terminal may acquire, by using the parent application,the jump path used for recording one or more existing child applicationjumping relationships, traverse child application identifiers in theacquired jump path, and compare a traversed-to child applicationidentifier with the acquired child application identifier. The parentapplication detects whether a next child application identifier of thetraversed-to child application identifier is a native plug-in childapplication identifier when determining that the traversed-to childapplication identifier is the same as the acquired child applicationidentifier.

The consecutive native plug-in child application identifier of thenative plug-in child application identifier is determined if the parentapplication determines that the next child application identifier of thetraversed-to child application identifier in the jump path is a nativeplug-in child application identifier, the acquired child applicationidentifier is then moved to the end of the jump path, and theconsecutive native plug-in child application identifier is deleted inthe jump path. The acquired child application identifier is directlymoved to the end of the jump path if the parent application determinesthat the next child application identifier of the traversed-to childapplication identifier in the jump path is not a native plug-in childapplication identifier.

That is, the native plug-in child application is configured to implementa function of the parent application or a child application. An adjacentand consecutive native plug-in child application identifier after thechild application identifier is also deleted when a position of a childapplication identifier needs to be moved.

For example, it is assumed that the jump path acquired by the terminalby using the parent application is “A→B→K1→K2→C”, where K1 and K2 arenative plug-in child application identifiers. If it is currentlyintended to jump from the child application corresponding to C to thechild application corresponding to B, in this case, B exists in“A→B→K1→K2→C”, and a next child application identifier of B is K1 and isa native plug-in child application identifier. It is determined thatconsecutive native plug-in child application identifiers after B are“K1→K2”, so that B is moved to the end of “A→B→K1→K2→C”, and “K1→K2” aredeleted to obtain “A→C→B”.

If it is currently intended to jump from the child applicationcorresponding to C to a native plug-in child application correspondingto K1, in this case, K1 exists in “A→B→K1→K2→C”, and a next childapplication identifier of K1 is K2 and is a native plug-in childapplication identifier. It is determined that the consecutive nativeplug-in child application identifier after K1 is “K2”, so that K1 ismoved to the end of “A→B→K1→K2→C”, and “K2” is deleted to obtain“A→B→C→K1”.

If it is currently intended to jump from the child applicationcorresponding to C to a native plug-in child application correspondingto K2, in this case, K2 exists in “A→B→K1→K2→C”, and a next childapplication identifier of K2 is C and is not a native plug-in childapplication identifier. K2 is directly moved to the end of “A→B→K1→K2→C”to obtain “A→B→K1→C→K2”.

In some embodiments, the native plug-in child application that may beused as a child application component is provided, so that useexperience basically consistent with that of directly using a childapplication may be achieved when a jump is made from the childapplication to the native plug-in child application, so that a processof developing a child application is avoided, and efficiency ofimplementing a child application is improved.

In an embodiment, the child application further includes a third-partychild application, and the application processing method furtherincludes: monitoring a close instruction by using the child applicationto which a currently displayed child application page belongs; returningto the native plug-in child application corresponding to a nativeplug-in child application identifier when a close instruction isdetected and the native plug-in child application identifier (that is, afirst native plug-in child application identifier) exists before aforemost third-party child application identifier in the jump path; andreturning to the parent application when a close instruction is detectedand a native plug-in child application identifier does not exist beforethe foremost third-party child application identifier in the jump path.

The third-party child application is a child application developed by athird-party service provider registered on an open service platformcorresponding to the parent application. The close instruction is aninstruction used for closing a child application and return to theparent application or the native plug-in child application.

For example, the parent application is WeChat, and the third-party childapplication is a bicycle sharing application, an XXXX shoppingapplication or the like. The user may scan a two-dimensional barcode,search for a name (for example, Mobike) of the third-party childapplication, click a message or a contact card shared by another user orperform another operation in WeChat to download and run the third-partychild application, so as to use a service provided by the third-partychild application. The third-party child application seamlessly accessesthe parent application and is referred to as a part of the parentapplication, so that the user has native experience and the third-partychild application has fully extended functions of the parentapplication. For example, Mobike may be used in WeChat to use a sharedbicycle or the XXXX shopping application may be used in WeChat to doshopping.

In an embodiment, the terminal may monitor or listen to, by using thechild application to which the currently displayed child applicationpage belongs, an event triggered in the currently displayed childapplication page. The event is used for triggering closing of a childapplication and returning to the parent application or the nativeplug-in child application. The event may be a trigger operation on anoperation portal such as an icon (for example, the control 500 in FIG.5) or a virtual button. The jump path becomes invalid when an event usedfor triggering closing of a child application is detected or heard. Forexample, the jump path is A→B→C, and the child application C iscurrently displayed. The jump path A→B→C becomes invalid when it isdetected that the user operates the control 500 in FIG. 5 (that is,closes the child application C), and a return is made to the parentapplication.

Specifically, after detecting or hearing a close instruction by usingthe child application to which the currently displayed child applicationpage belongs, the terminal searches the jump path by using the parentapplication to determine whether a native plug-in child applicationidentifier exists before the first third-party child applicationidentifier; and returns to a native plug-in child applicationcorresponding to a native plug-in child application identifier if thenative plug-in child application identifier exists before the foremostthird-party child application identifier in the jump path, or returns tothe parent application if a native plug-in child application identifierdoes not exist before the foremost third-party child applicationidentifier in the jump path.

In an embodiment, the returning to a native plug-in child applicationcorresponding to a native plug-in child application identifier includes:acquiring a native plug-in child application identifier (that is, asecond native plug-in child application identifier) that is adjacent tothe first third-party child application identifier and is located beforethe first third-party child application identifier when more than onenative plug-in child application identifier exists before the foremostthird-party child application identifier in the jump path; determining anative plug-in child application page displayed during a jump by anative plug-in child application corresponding to the acquired nativeplug-in child application identifier; and displaying the determinednative plug-in child application page.

Specifically, when finding, by using the parent application, that anative plug-in child application identifier exists before the foremostthird-party child application identifier in the jump path, the terminaldetermines whether more than one native plug-in child applicationidentifier exists before the foremost third-party child applicationidentifier in the jump path. If determining, by using the parentapplication, that there is only one native plug-in child applicationidentifier, the terminal displays the native plug-in child applicationpage displayed during a jump by a native plug-in child applicationcorresponding to the unique native plug-in child application identifier.

If determining, by using the parent application, that there is more thanone native plug-in child application identifier, the terminal acquires anative plug-in child application identifier that is adjacent to thefirst third-party child application identifier and is located before thefirst third-party child application identifier; determines the nativeplug-in child application page displayed during a jump by the nativeplug-in child application corresponding to the acquired native plug-inchild application identifier; and displays the determined native plug-inchild application page.

In some embodiments, because the native plug-in child application isconfigured to implement a function of the parent application and thenative plug-in child application and the parent application areconsidered as a whole, a direct return is made to the parent applicationor the native plug-in child application when it is intended to close arunning third-party child application, and indirect control using thethird-party child application is not required, so that application useefficiency is improved.

In the foregoing embodiment, it is only necessary to trigger a closeinstruction to directly return to the parent application or the nativeplug-in child application when the child application jump is completedand it is intended to close a running third-party child application, sothat the time required to close third-party child applications one byone is avoided, and application use efficiency is improved.

FIG. 5 is a schematic diagram of closing a child application accordingto an embodiment. Referring to FIG. 5, the schematic diagram includes aclose trigger portal 500, a currently displayed child application page501, a native plug-in child application page 502 displayed during a jumpby a native plug-in child application corresponding to a native plug-inchild application identifier that is adjacent to the first third-partychild application identifier in the jump path and is located before thefirst third-party child application identifier, and a parent applicationpage 503 displayed by the parent application when running a childapplication.

After detecting the trigger operation on the close trigger portal 500 onthe currently displayed child application page 501 and detecting, byusing the parent application, that a native plug-in child applicationidentifier exists before the first third-party child applicationidentifier in the jump path, the terminal returns to, according to theclose instruction, the native plug-in child application page 502displayed during a jump by the native plug-in child applicationcorresponding to the native plug-in child application identifier that isadjacent to the first third-party child application identifier in thejump path and is located before the first third-party child applicationidentifier. When detecting, by using the parent application, that anative plug-in child application identifier does not exist before thefirst third-party child application identifier in the jump path, theterminal returns to the parent application page 503 displayed by theparent application when running the child application.

In an embodiment, the transferring page data corresponding to the childapplication identifier to the child application that corresponds to thechild application identifier and is run by the parent applicationincludes: switching to the parent application page used for triggering achild application jump, where the parent application page is a pagedisplayed by the parent application; triggering, by using the parentapplication page, acquisition of page data corresponding to the childapplication identifier; and transferring the page data to the childapplication that corresponds to the child application identifier and isrun by the parent application.

Specifically, the parent application page is used for triggering thechild application jump. That is, it is necessary to first switch to theparent application page and the parent application page is then used fortriggering acquisition of the page data corresponding to the childapplication identifier when it is intended to jump from a childapplication to another child application. The page data is thentransferred to the child application that corresponds to the childapplication identifier and is run by the parent application.

The parent application page used for triggering a child application jumpmay be a universal parent application page. By using the universalparent application page, it may be triggered to start to jump to anychild application. The parent application page used for triggering achild application jump may be alternatively parent application pagesthat correspond to child applications one by one. Each child applicationhas one corresponding parent application page used for starting thechild application.

In some embodiments, a switch is made to the parent application pageused for triggering a child application jump to implement a childapplication jump, thereby providing a new way for a child applicationjump.

FIG. 6 is a schematic diagram of jumping to a child applicationaccording to an embodiment. Referring to FIG. 6, the schematic diagramincludes a currently displayed child application page 601, a parentapplication page 602 used for triggering a child application jump, and achild application page 603 corresponding to a child application to bejumped to. The terminal switches from the child application page 601currently displayed in a current child application to the parentapplication page 602 used for triggering a child application jump andthen triggers a jump to the child application page 603 corresponding tothe child application to be jumped to, thereby implementing a childapplication jump.

In an embodiment, after S204, the application processing method furtherincludes: acquiring a parent application page identifier (that is, afirst parent application page identifier) corresponding to a switched-toparent application page (that is, a first parent application page) and ajump path used for recording one or more existing child applicationjumping relationships; deleting a parent application page identifier(that is, a second parent application page identifier) that is adjacentto the acquired child application identifier in the jump path and islocated after the acquired child application identifier when theacquired child application identifier exists in the jump path; andadding the acquired parent application page identifier to the end of thejump path; and moving the child application identifier acquired in thejump path after the added parent application page identifier.

The jump path includes child application identifiers and/or parentapplication page identifiers arranged in a child application jumpsequence, records a child application jumping relationship, and reflectsa child application jump manner. For example, the jump path recordingthe child application jumping relationship of “switching from the childapplication A to a parent application page M to jump to the childapplication C” is: A→M→C.

Specifically, the terminal may acquire, by using the parent application,the jump path used for recording one or more existing child applicationjumping relationships, traverse child application identifiers in theacquired jump path, and compare a traversed-to child applicationidentifier with the acquired child application identifier. Whendetermining that the traversed-to child application identifier is thesame as the acquired child application identifier, the parentapplication deletes an adjacent parent application page identifier afterthe traversed-to child application identifier, adds the parentapplication page identifier corresponding to the switched-to parentapplication page after the end of the jump path, and moves thetraversed-to child application identifier after the added parentapplication page identifier.

When determining that no traversed-to child application identifier isthe same as the acquired child application identifier, the parentapplication directly adds the parent application page identifiercorresponding to the switched-to parent application page and theacquired child application identifier in sequence to the end of the jumppath.

For example, it is assumed that the jump path acquired by the terminalby using the parent application is “A→M1→B→C”. If it is currentlyintended to jump from the child application corresponding to C to achild application corresponding to A via a parent application page M2,in this case, A exists in “A→M1→B→C”. An adjacent parent applicationpage M1 after A is deleted. After M2 is added after the end of “A→B→C”and A is moved after M2, “B→C→M2→A” is obtained.

In some embodiments, during a child application jump in an environmentprovided by the parent application, the child application jumpingrelationship reflecting the child application jump manner is recorded,so as to return to accessed child applications or parent applicationpages sequentially.

In other embodiments, a parent application page identifier of a parentapplication page and a child application identifier of a jumped-to childapplication are both recorded in a jump path when a jump from a childapplication to another child application is triggered by a switch to theparent application page. No data is transferred when a child applicationreturn is triggered by invoking the return interface provided by theparent application. If a current child application that needs to bereturned to, that is, the child application to be returned to determinedaccording to the jump path, is not a source child application forjumping to the current child application that needs to be returned to,no data is transferred either when a child application return istriggered by invoking the return interface provided by the parentapplication.

FIG. 7 is a schematic flowchart of an application processing methodaccording to a specific embodiment. Referring to FIG. 7, the applicationprocessing method specifically includes the following steps:

S702: Display a child application page of a child application run by aparent application, the child application including a native plug-inchild application and a third-party child application.

S704: Acquire, by using the child application, a child applicationidentifier (for example, an APP ID) corresponding to a child applicationto be jumped to.

S706: Detect a child application jump manner, perform step S708 if thechild application jump manner is a jump by invoking an interface (forexample, launch JSAPI) provided by the parent application; and performstep S722 if the child application jump manner is a jump triggered byusing a parent application page.

S708: Transfer page data corresponding to the child applicationidentifier to the child application that corresponds to the childapplication identifier and is run by the parent application.

S710: Acquire a jump path used for recording one or more existing childapplication jumping relationships.

S712: Detect whether the acquired child application identifier exists inthe jump path; and perform step S714 if yes; or perform step S720 ifnot.

S714: Detect whether there is an adjacent native plug-in childapplication after the acquired child application identifier; and performstep S716 if yes; or perform step S718 if not.

S716: Determine a consecutive native plug-in child applicationidentifier that is adjacent to the acquired child application identifierin the jump path and is located after the acquired child applicationidentifier; and move the acquired child application identifier to theend of the jump path, and delete the consecutive native plug-in childapplication identifier in the jump path.

S718: Move the acquired child application identifier to the end of thejump path.

S720: Add the acquired child application identifier to the end of thejump path.

S722: Switch to the parent application page used for triggering a childapplication jump; trigger, by using the parent application page,acquisition of page data corresponding to the child applicationidentifier; and transfer the page data to the child application thatcorresponds to the child application identifier and is run by the parentapplication.

S724: Acquire a parent application page identifier corresponding to aswitched-to parent application page and a jump path used for recordingone or more existing child application jumping relationships.

S726: Detect whether the acquired child application identifier exists inthe jump path; and perform step S728 if yes; or perform step S730 ifnot.

S728: Delete a parent application page identifier that is adjacent tothe acquired child application identifier in the jump path and islocated after the acquired child application identifier; add theacquired parent application page identifier to the end of the jump path;and move the child application identifier acquired in the jump pathafter the added parent application page identifier.

S730: Add the acquired parent application page identifier and the childapplication identifier sequentially to the end of the jump path.

S732: Generate, by using the child application corresponding to thechild application identifier and according to the page data, a childapplication page displayed over the displayed child application page.

S734: Acquire a return instruction by using a child application to whicha currently displayed child application page belongs; in response to thereturn instruction, determine the child application identifiercorresponding to the currently displayed child application page; andsearch the jump path for a child application identifier that is adjacentto the determined child application identifier and is located before thedetermined child application identifier.

S736: Detect a running state of the child application corresponding tothe found child application identifier; perform step S738 if the childapplication corresponding to the found child application identifier isrun by the parent application in a background state; and perform stepS740 if the child application corresponding to the found childapplication identifier has finished running.

S738: Return to a child application page displayed during a jump by thechild application corresponding to the found child applicationidentifier.

S740: Return to a default child application page corresponding to thefound child application identifier.

S742: Monitor a close instruction by using the child application towhich a currently displayed child application page belongs.

S744: Detect whether a native plug-in child application identifierexists before a first third-party child application identifier in thejump path when a close instruction is detected; and perform step S746 ifyes; or perform step S752 if not.

S746: Detect whether more than one native plug-in child applicationidentifier exists before the first third-party child applicationidentifier in the jump path; and perform step S748 if yes; or performstep S750 if not.

S748: Acquire a native plug-in child application identifier that isadjacent to the first third-party child application identifier and islocated before the first third-party child application identifier;determine a native plug-in child application page displayed during ajump by a native plug-in child application corresponding to the acquirednative plug-in child application identifier; and display the determinednative plug-in child application page.

S750: Return to the native plug-in child application corresponding tothe native plug-in child application identifier.

S752: Return to the parent application.

In some embodiments, the parent application runs on the OS, a childapplication may be run by the parent application, and a childapplication page that belongs to the child application is displayed. Theparent application only needs to acquire, by using the childapplication, a child application identifier corresponding to a childapplication to be jumped to before the parent application can transferpage data corresponding to the child application identifier to the childapplication that corresponds to the child application identifier and isrun by the parent application when it is necessary to make a childapplication jump, and the child application corresponding to the childapplication identifier may then generate, according to the page data, achild application page displayed over the displayed child applicationpage, so as to automatically implement the child application jump. Thetime required to exit a currently used application and then start anintended application to be jumped to is avoided, and application useefficiency is improved.

In addition, a processing manner of jumping from a child application andthen returning to the child application is provided, so that a returnmay be directly made in the parent application when it is intended toreturn to a used child application, the time required to exit acurrently used application and then start an intended application to bereturned to is avoided, and application use efficiency is improved. Itis only necessary to trigger a close instruction to directly return tothe parent application or the native plug-in child application when thechild application jump is completed and it is intended to close arunning third-party child application, so that the time required toclose third-party child applications one by one is avoided, andapplication use efficiency is improved.

As shown in FIG. 8, in an embodiment, an application processingapparatus 800 is provided. Referring to FIG. 8, the applicationprocessing apparatus 800 includes a parent application 810.

The parent application 810 is configured to: display a child applicationpage of a running child application; acquire, by using the childapplication, a child application identifier corresponding to a childapplication to be jumped to; transfer page data corresponding to thechild application identifier to the child application that correspondsto the child application identifier and is run by the parentapplication; and generate, by using the child application correspondingto the child application identifier and according to the page data, achild application page displayed over the displayed child applicationpage.

For the foregoing application processing apparatus 800, the parentapplication runs on the OS, a child application may be run by the parentapplication, and a child application page that belongs to the childapplication is displayed. The parent application only needs to acquire,by using the child application, a child application identifiercorresponding to a child application to be jumped to before the parentapplication can transfer page data corresponding to the childapplication identifier to the child application that corresponds to thechild application identifier and is run by the parent application whenit is necessary to make a child application jump, and the childapplication corresponding to the child application identifier may thengenerate, according to the page data, a child application page displayedover the displayed child application page, so as to automaticallyimplement the child application jump. The time required to exit acurrently used application and then start an intended application to bejumped to is avoided, and application use efficiency is improved.

In an embodiment, the parent application 810 is further configured toacquire a jump path used for recording one or more existing childapplication jumping relationships; move the acquired child applicationidentifier to the end of the jump path when the acquired childapplication identifier exists in the jump path; and add the acquiredchild application identifier to the end of the jump path when theacquired child application identifier does not exist in the jump path.

In some embodiments, during a child application jump in an environmentprovided by the parent application, and the child application jumpingrelationship is recorded, so as to return to accessed child applicationssequentially.

In an embodiment, the parent application 810 is further configured to:acquire a return instruction by using a child application to which acurrently displayed child application page belongs; in response to thereturn instruction, determine the child application identifiercorresponding to the currently displayed child application page; searchthe jump path for a child application identifier that is adjacent to thedetermined child application identifier and is located before thedetermined child application identifier; and return to the childapplication page corresponding to the found child applicationidentifier.

In some embodiments, a processing manner of jumping from a childapplication and then returning to the child application is provided, sothat a return may be directly made in the parent application when it isintended to return to a used child application, and the time required toexit a currently used application and then start an intended applicationto be returned to is avoided, and application use efficiency isimproved.

In an embodiment, the parent application 810 is further configured to:return to a child application page displayed during a jump by the childapplication corresponding to the found child application identifier whenthe child application corresponding to the found child applicationidentifier is run by the parent application in a background state; andreturn to a default child application page corresponding to the foundchild application identifier when the child application corresponding tothe found child application identifier has finished running.

In some embodiments, the child application may be switched to theforeground for running to swiftly return to a page displayed by thechild application to be returned to during the jump when the childapplication to be returned to is still run in the background, so that auser may continue to operate on the page, thereby improving applicationconvenience. In addition, the default child application page of thechild application to be returned to is directly returned to in theparent application when the child application to be returned to hasfinished running, so that the time for manual switching is avoided, andapplication use efficiency is improved.

In an embodiment, the child application includes a native plug-in childapplication, and the parent application 810 is further configured to:determine a consecutive native plug-in child application identifier thatis adjacent to the acquired child application identifier in the jumppath and is located after the acquired child application identifier whenthe acquired child application identifier exists in the jump path; andmove the acquired child application identifier to the end of the jumppath, and delete the consecutive native plug-in child applicationidentifier in the jump path.

In some embodiments, the native plug-in child application that may beused as a child application component is provided, so that useexperience when a jump is made from the child application to the nativeplug-in child application basically consistent with that of directlyusing a child application may be achieved, a process of developing achild application is avoided, and efficiency of implementing a childapplication is improved.

In an embodiment, the child application further includes a third-partychild application. The parent application 810 is further configured to:monitor a close instruction by using the child application to which acurrently displayed child application page belongs; return to the nativeplug-in child application corresponding to a native plug-in childapplication identifier when a close instruction is detected and thenative plug-in child application identifier exists before a firstthird-party child application identifier in the jump path; and return tothe parent application when a close instruction is detected and a nativeplug-in child application identifier does not exist before the firstthird-party child application identifier in the jump path.

In some embodiments, it is only necessary to trigger a close instructionto directly return to the parent application or the native plug-in childapplication when a child application jump is completed and it isintended to close a running third-party child application, so that thetime required to close third-party child applications one by one isavoided, and application use efficiency is improved.

In an embodiment, the parent application 810 is further configured to:acquire a native plug-in child application identifier that is adjacentto the first third-party child application identifier and is locatedbefore the first third-party child application identifier when more thanone native plug-in child application identifier exists before the firstthird-party child application identifier in the jump path; determine anative plug-in child application page displayed during a jump by anative plug-in child application corresponding to the acquired nativeplug-in child application identifier; and display the determined nativeplug-in child application page.

In some embodiments, because the native plug-in child application isconfigured to implement a function of the parent application and thenative plug-in child application and the parent application areconsidered as a whole, a direct return is made to the parent applicationor the native plug-in child application when it is intended to close arunning third-party child application, and indirect control using thethird-party child application is not required, so that application useefficiency is improved.

In an embodiment, the parent application 810 is further configured to:switch to a parent application page used for triggering a childapplication jump; trigger, by using the parent application page,acquisition of page data corresponding to the child applicationidentifier; and transfer the page data to the child application thatcorresponds to the child application identifier and is run by the parentapplication.

In some embodiments, a switch is made to the parent application pageused for triggering a child application jump to implement a childapplication jump, thereby providing a new way for a child applicationjump.

In an embodiment, the parent application 810 is further configured to:acquire a parent application page identifier corresponding to aswitched-to parent application page and a jump path used for recordingone or more existing child application jumping relationships; delete aparent application page identifier that is adjacent to the acquiredchild application identifier in the jump path and is located after theacquired child application identifier when the acquired childapplication identifier exists in the jump path; add the acquired parentapplication page identifier to the end of the jump path; and move thechild application identifier acquired in the jump path after the addedparent application page identifier.

In some embodiments, during a child application jump in an environmentprovided by the parent application, the child application jumpingrelationship reflecting a child application jump manner is recorded, soas to return to accessed child applications or parent application pagessequentially.

As shown in FIG. 9, in an embodiment, a structural modular diagram ofthe parent application 810 is provided. Referring to FIG. 9, the parentapplication 810 includes a display module 801, an acquisition module802, a transfer module 803, and a jump module 804.

The display module 801 is configured to display a child application pageof a running child application.

The acquisition module 802 is configured to acquire, by using the childapplication, a child application identifier corresponding to a childapplication to be jumped to.

The transfer module 803 is configured to transfer page datacorresponding to the child application identifier to the childapplication that corresponds to the child application identifier and isrun by the parent application.

The jump module 804 is configured to generate, by using the childapplication corresponding to the child application identifier andaccording to the page data, a child application page displayed over thedisplayed child application page.

For the foregoing parent application 810, a child application may be runby the parent application, and a child application page that belongs tothe child application is displayed. The parent application only needs toacquire, by using the child application, a child application identifiercorresponding to a child application to be jumped to before the parentapplication can transfer page data corresponding to the childapplication identifier to the child application that corresponds to thechild application identifier and is run by the parent application whenit is necessary to make a child application jump, and the childapplication corresponding to the child application identifier may thengenerate, according to the page data, a child application page displayedover the displayed child application page, so as to automaticallyimplement the child application jump. The time required to exit acurrently used application and then start an intended application to bejumped to is avoided, and application use efficiency is improved.

In an embodiment, the acquisition module 802 is further configured toacquire a jump path used for recording one or more existing childapplication jumping relationships; move the acquired child applicationidentifier to the end of the jump path when the acquired childapplication identifier exists in the jump path; and add the acquiredchild application identifier to the end of the jump path when theacquired child application identifier does not exist in the jump path.

In some embodiments, during the child application jump in the parentapplication, and the child application jumping relationship is recorded,so as to return to accessed child applications sequentially.

As shown in FIG. 10, in an embodiment, the parent application 810further includes an instruction processing module 805.

The instruction processing module 805 is configured to: acquire a returninstruction by using a child application to which a currently displayedchild application page belongs; in response to the return instruction,determine the child application identifier corresponding to thecurrently displayed child application page; search the jump path for achild application identifier that is adjacent to the determined childapplication identifier and is located before the determined childapplication identifier; and return to the child application pagecorresponding to the found child application identifier.

In some embodiments, a processing manner of jumping from a childapplication and then returning to the child application is provided, sothat a return may be directly made in the parent application when it isintended to return to a used child application, and the time required toexit a currently used application and then start an intended applicationto be returned to is avoided, and application use efficiency isimproved.

In an embodiment, the instruction processing module 805 is furtherconfigured to: return to a child application page displayed during ajump by the child application corresponding to the found childapplication identifier when the child application corresponding to thefound child application identifier is run by the parent application in abackground state; and return to a default child application pagecorresponding to the found child application identifier when the childapplication corresponding to the found child application identifier hasfinished running.

In some embodiments, the child application may be switched to theforeground for running to swiftly return to a page displayed by thechild application to be returned to during the jump when the childapplication to be returned to is still run in the background, so thatthe user may continue to operate on the page, thereby improvingapplication convenience. In addition, the default child application pageof the child application to be returned to is directly returned to inthe parent application when the child application to be returned to hasfinished running, so that the time for manual switching is avoided, andapplication use efficiency is improved.

In an embodiment, the child application includes a native plug-in childapplication, and the acquisition module 802 is further configured to:determine a consecutive native plug-in child application identifier thatis adjacent to the acquired child application identifier in the jumppath and is located after the acquired child application identifier whenthe acquired child application identifier exists in the jump path; andmove the acquired child application identifier to the end of the jumppath, and delete the consecutive native plug-in child applicationidentifier in the jump path.

In some embodiments, the native plug-in child application that may beused as a child application component is provided, so that during a jumpfrom the child application to the native plug-in child application, useexperience basically consistent with that of directly using a childapplication may be achieved, so that a process of developing a childapplication is avoided, and efficiency of implementing a childapplication is improved.

In an embodiment, the child application further includes a third-partychild application. The instruction processing module 805 is furtherconfigured to: monitor a close instruction by using the childapplication to which a currently displayed child application pagebelongs; return to the native plug-in child application corresponding toa native plug-in child application identifier when a close instructionis detected and the native plug-in child application identifier existsbefore a first third-party child application identifier in the jumppath; and return to the parent application when a close instruction isdetected and a native plug-in child application identifier does notexist before the first third-party child application identifier in thejump path.

In some embodiments, it is only necessary to trigger a close instructionto directly return to the parent application or the native plug-in childapplication when the child application jump is completed and it isintended to close a running third-party child application, so that thetime required to close third-party child applications one by one isavoided, and application use efficiency is improved.

In an embodiment, the instruction processing module 805 is furtherconfigured to: acquire a native plug-in child application identifierthat is adjacent to the first third-party child application identifierand is located before the first third-party child application identifierwhen more than one native plug-in child application identifier existsbefore the first third-party child application identifier in the jumppath; determine a native plug-in child application page displayed duringa jump by a native plug-in child application corresponding to theacquired native plug-in child application identifier; and display thedetermined native plug-in child application page.

In some embodiments, the native plug-in child application is configuredto implement a function of the parent application and the native plug-inchild application and the parent application are considered as a whole,a direct return is made to the parent application or the native plug-inchild application when it is intended to close a running third-partychild application, and indirect control using the third-party childapplication is not required, so that application use efficiency isimproved.

In an embodiment, the transfer module 803 is further configured to:switch to a parent application page used for triggering a childapplication jump; trigger, by using the parent application page,acquisition of page data corresponding to the child applicationidentifier; and transfer the page data to the child application thatcorresponds to the child application identifier and is run by the parentapplication.

In some embodiments, a switch is made to the parent application pageused for triggering a child application jump to implement a childapplication jump, thereby providing a new way for a child applicationjump.

In an embodiment, the acquisition module 802 is further configured to:acquire a parent application page identifier corresponding to theswitched-to parent application page and a jump path used for recordingone or more existing child application jumping relationships; delete aparent application page identifier that is adjacent to the acquiredchild application identifier in the jump path and is located after theacquired child application identifier when the acquired childapplication identifier exists in the jump path; add the acquired parentapplication page identifier to the end of the jump path; and move thechild application identifier acquired in the jump path after the addedparent application page identifier.

In some embodiments, during a child application jump in an environmentprovided by the parent application, the child application jumpingrelationship reflecting a child application jump manner is recorded, soas to return to accessed child applications or parent application pagessequentially.

FIG. 11 is an internal structural diagram of a computer device accordingto an embodiment. The computer device may be specifically the terminal110 in FIG. 1. As shown in FIG. 11, the computer device 1100 includes aprocessor 1101, a non-volatile storage medium 1102, an internal memory1103, a network interface 1104, and a display screen 1105 that areconnected via a system bus. The non-volatile storage medium 1102 of thecomputer device 1100 may store an OS 1106 and computer readableinstructions 1107. When being executed, the computer readableinstructions 1107 enable the processor 1101 to perform an applicationprocessing method. The processor 1101 is configured to provide computingand control capabilities to supporting the running of the entirecomputer device. The internal memory 1103 may store the computerreadable instructions 1107. When being executed by the processor 1101,the computer readable instructions 1107 may enable the processor 1101 toperform the application processing method. The network interface 1104 isconfigured to perform network communication with a server, for example,send a collaborative operation authorization request to the server, andreceive an authorization response returned by the server. A displayscreen of the computer device 1100 may be a liquid crystal displayscreen, an electronic ink display screen or the like. The computerdevice 1100 may be a mobile phone, a tablet computer, a personal digitalassistant, a wearable device or the like. A person skilled in the artmay understand that the structure shown in FIG. 11 is only a blockdiagram of a partial structure related to the solution in the presentapplication, but do not constitute a limitation to the computer deviceto which the solution in the present application is applied. A specificcomputer device may include more or fewer components than those in thefigure, or some components may be combined, or a different componentdeployment may be used.

In an embodiment, the application processing apparatus provided in thepresent application may be implemented in the form of a computerprogram. The computer program may be executed by the computer device1100 shown in FIG. 11. A non-volatile storage medium of the computerdevice may store program modules that form the application processingapparatus, for example, the parent application 810 shown in FIG. 8. Theprogram modules include computer readable instructions. The computerreadable instructions are used for enabling the computer device toperform the steps in the application processing method in theembodiments of the present application described in the specification.For example, the computer device may display, by using the parentapplication 810 in the application processing apparatus 800 shown inFIG. 8, a child application page of a running child application;acquire, by using the child application, a child application identifiercorresponding to a child application to be jumped to; transfer page datacorresponding to the child application identifier to the childapplication that corresponds to the child application identifier and isrun by the parent application; and generate, by using the childapplication corresponding to the child application identifier andaccording to the page data, a child application page displayed over thedisplayed child application page.

In an embodiment, a computer readable storage medium is provided. Thecomputer readable storage medium stores computer readable instructions.When being executed by a processor, the computer readable instructionsenable the processor to perform the following steps: displaying a childapplication page of a child application run by a parent application;acquiring, by using the child application, a child applicationidentifier corresponding to a child application to be jumped to;transferring page data corresponding to the child application identifierto the child application that corresponds to the child applicationidentifier and is run by the parent application; and generating, byusing the child application corresponding to the child applicationidentifier and according to the page data, a child application pagedisplayed over the displayed child application page.

In an embodiment, the computer readable instructions enable theprocessor to further perform, after the acquiring, by using the childapplication, a child application identifier corresponding to a childapplication to be jumped to, the following steps: acquiring a jump pathused for recording one or more existing child application jumpingrelationships; moving the acquired child application identifier to theend of the jump path when the acquired child application identifierexists in the jump path; and adding the acquired child applicationidentifier to the end of the jump path when the acquired childapplication identifier does not exist in the jump path.

In an embodiment, the computer readable instructions further enable theprocessor to perform the following steps: acquiring a return instructionby using a child application to which a currently displayed childapplication page belongs; in response to the return instruction,determining the child application identifier corresponding to thecurrently displayed child application page; searching the jump path fora child application identifier that is adjacent to the determined childapplication identifier and is located before the determined childapplication identifier; and returning to the child application pagecorresponding to the found child application identifier.

In an embodiment, the returning to the child application pagecorresponding to the found child application identifier includes:returning to a child application page displayed during a jump by thechild application corresponding to the found child applicationidentifier when the child application corresponding to the found childapplication identifier is run by the parent application in a backgroundstate; and returning to a default child application page correspondingto the found child application identifier when the child applicationcorresponding to the found child application identifier has finishedrunning.

In an embodiment, the child application includes a native plug-in childapplication, and the moving the acquired child application identifier tothe end of the jump path when the acquired child application identifierexists in the jump path includes: determining a consecutive nativeplug-in child application identifier that is adjacent to the acquiredchild application identifier in the jump path and is located after theacquired child application identifier when the acquired childapplication identifier exists in the jump path; and moving the acquiredchild application identifier to the end of the jump path, and deletingthe consecutive native plug-in child application identifier in the jumppath.

In an embodiment, the child application further includes a third-partychild application. The computer readable instructions further enable theprocessor to perform the following steps: monitoring a close instructionby using a child application to which the currently displayed childapplication page belongs; returning to the native plug-in childapplication corresponding to a native plug-in child applicationidentifier when a close instruction is detected and the native plug-inchild application identifier exists before a first third-party childapplication identifier in the jump path; and returning to the parentapplication when a close instruction is detected and a native plug-inchild application identifier does not exist before the first third-partychild application identifier in the jump path.

In an embodiment, the returning to a native plug-in child applicationcorresponding to a native plug-in child application identifier includes:acquiring a native plug-in child application identifier that is adjacentto the first third-party child application identifier and is locatedbefore the first third-party child application identifier when more thanone native plug-in child application identifier exists before the firstthird-party child application identifier in the jump path; determining anative plug-in child application page displayed during a jump by anative plug-in child application corresponding to the acquired nativeplug-in child application identifier; and displaying the determinednative plug-in child application page.

In an embodiment, the transferring page data corresponding to the childapplication identifier to the child application that corresponds to thechild application identifier and is run by the parent applicationincludes: switching to a parent application page used for triggering achild application jump; triggering, by using the parent applicationpage, acquisition of page data corresponding to the child applicationidentifier; and transferring the page data to the child application thatcorresponds to the child application identifier and is run by the parentapplication.

In an embodiment, the computer readable instructions enable theprocessor to further perform, after the acquiring, by using the childapplication, a child application identifier corresponding to a childapplication to be jumped to, the following steps: acquiring a parentapplication page identifier corresponding to a switched-to parentapplication page and a jump path used for recording one or more existingchild application jumping relationships; deleting a parent applicationpage identifier that is adjacent to the acquired child applicationidentifier in the jump path and is located after the acquired childapplication identifier when the acquired child application identifierexists in the jump path; adding the acquired parent application pageidentifier to the end of the jump path; and moving the child applicationidentifier acquired in the jump path after the added parent applicationpage identifier.

For the foregoing storage medium, a parent application runs on an OS, achild application may be run by the parent application, and a childapplication page that belongs to the child application is displayed. Theparent application only needs to acquire, by using the childapplication, a child application identifier corresponding to a childapplication to be jumped to before the parent application can transferpage data corresponding to the child application identifier to the childapplication that corresponds to the child application identifier and isrun by the parent application when it is necessary to make a childapplication jump, and the child application corresponding to the childapplication identifier may then generate, according to the page data, achild application page displayed over the displayed child applicationpage, so as to automatically implement the child application jump. Thetime required to exit a currently used application and then start anintended application to be jumped to is avoided, and application useefficiency is improved.

In an embodiment, a computer device is provided, including a memory anda processor. The memory stores computer readable instructions. Whenbeing executed by the processor, the computer readable instructionsenable the processor to perform the following steps: displaying a childapplication page of a child application run by a parent application;acquiring, by using the child application, a child applicationidentifier corresponding to a child application to be jumped to;transferring page data corresponding to the child application identifierto the child application that corresponds to the child applicationidentifier and is run by the parent application; and generating, byusing the child application corresponding to the child applicationidentifier and according to the page data, a child application pagedisplayed over the displayed child application page.

In an embodiment, the computer readable instructions enable theprocessor to further perform, after the acquiring, by using the childapplication, a child application identifier corresponding to a childapplication to be jumped to, the following steps: acquiring a jump pathused for recording one or more existing child application jumpingrelationships; moving the acquired child application identifier to theend of the jump path when the acquired child application identifierexists in the jump path; and adding the acquired child applicationidentifier to the end of the jump path when the acquired childapplication identifier does not exist in the jump path.

In an embodiment, the computer readable instructions further enable theprocessor to perform the following steps: acquiring a return instructionby using a child application to which a currently displayed childapplication page belongs; in response to the return instruction,determining the child application identifier corresponding to thecurrently displayed child application page; searching the jump path fora child application identifier that is adjacent to the determined childapplication identifier and is located before the determined childapplication identifier; and returning to the child application pagecorresponding to the found child application identifier.

In an embodiment, the returning to the child application pagecorresponding to the found child application identifier includes:returning to a child application page displayed during a jump by thechild application corresponding to the found child applicationidentifier when the child application corresponding to the found childapplication identifier is run by the parent application in a backgroundstate; and returning to a default child application page correspondingto the found child application identifier when the child applicationcorresponding to the found child application identifier has finishedrunning.

In an embodiment, the child application includes a native plug-in childapplication, and the moving the acquired child application identifier tothe end of the jump path when the acquired child application identifierexists in the jump path includes: determining a consecutive nativeplug-in child application identifier that is adjacent to the acquiredchild application identifier in the jump path and is located after theacquired child application identifier when the acquired childapplication identifier exists in the jump path; and moving the acquiredchild application identifier to the end of the jump path, and deletingthe consecutive native plug-in child application identifier in the jumppath.

In an embodiment, the child application further includes a third-partychild application. The computer readable instructions further enable theprocessor to perform the following steps: monitoring a close instructionby using the child application to which a currently displayed childapplication page belongs; returning to the native plug-in childapplication corresponding to a native plug-in child applicationidentifier when a close instruction is detected and the native plug-inchild application identifier exists before a first third-party childapplication identifier in the jump path; and returning to the parentapplication when a close instruction is detected and a native plug-inchild application identifier does not exist before the first third-partychild application identifier in the jump path.

In an embodiment, the returning to a native plug-in child applicationcorresponding to a native plug-in child application identifier includes:acquiring a native plug-in child application identifier that is adjacentto the first third-party child application identifier and is locatedbefore the first third-party child application identifier when more thanone native plug-in child application identifier exists before the firstthird-party child application identifier in the jump path; determining anative plug-in child application page displayed during a jump by anative plug-in child application corresponding to the acquired nativeplug-in child application identifier; and displaying the determinednative plug-in child application page.

In an embodiment, the transferring page data corresponding to the childapplication identifier to the child application that corresponds to thechild application identifier and is run by the parent applicationincludes: switching to a parent application page used for triggering achild application jump; triggering, by using the parent applicationpage, acquisition of page data corresponding to the child applicationidentifier; and transferring the page data to the child application thatcorresponds to the child application identifier and is run by the parentapplication.

In an embodiment, the computer readable instructions enable theprocessor to further perform, after the acquiring, by using the childapplication, a child application identifier corresponding to a childapplication to be jumped to, the following steps: acquiring a parentapplication page identifier corresponding to a switched-to parentapplication page and a jump path used for recording one or more existingchild application jumping relationships; deleting a parent applicationpage identifier that is adjacent to the acquired child applicationidentifier in the jump path and is located after the acquired childapplication identifier when the acquired child application identifierexists in the jump path; adding the acquired parent application pageidentifier to the end of the jump path; and moving the child applicationidentifier acquired in the jump path after the added parent applicationpage identifier.

For the foregoing computer device, a parent application runs on an OS, achild application may be run by the parent application, and a childapplication page that belongs to the child application is displayed. Theparent application only needs to acquire, by using the childapplication, a child application identifier corresponding to a childapplication to be jumped to before the parent application can transferpage data corresponding to the child application identifier to the childapplication that corresponds to the child application identifier and isrun by the parent application when it is necessary to make a childapplication jump, and the child application corresponding to the childapplication identifier may then generate, according to the page data, achild application page displayed over the displayed child applicationpage, so as to automatically implement the child application jump. Thetime required to exit a currently used application and then start anintended application to be jumped to is avoided, and application useefficiency is improved.

A person of ordinary skill in the art may understand that all or some ofthe processes of the methods in the foregoing embodiments may beimplemented by a computer program instructing relevant hardware. Theprogram may be stored in a non-volatile computer-readable storagemedium. When the program is executed, the processes of the foregoingmethods in the embodiments are performed. The storage medium may be amagnetic disk, an optical disc, a Read-Only Memory (ROM), and the like.

The technical features of the foregoing embodiments may be randomlycombined. For the purpose of concise descriptions, not all possiblecombinations of the technical features in the foregoing embodiments aredescribed, but as long as combinations of the technical features do notconflict each other, the combinations of the technical features shouldbe considered as falling within the scope of this specification.

The foregoing embodiments show only several implementations of thepresent application, and descriptions thereof are in detail, but shallnot be understood as limiting the patent scope of the presentapplication. It should be noted that various changes and improvementsmay further be made by a person of ordinary skill in the art withoutdeparting from the idea of the present application, and these changesand improvements all fall within the protection scope of the presentapplication. Therefore, the protection scope of the present applicationshall be subject to the appended claims.

What is claimed is:
 1. An application processing method, applied to aterminal, the method comprising: displaying a first child applicationpage of a first child application, the first child application being runby a parent application; acquiring, by the first child application, asecond child application identifier corresponding to a second childapplication to be jumped to; running, by the parent application, thesecond child application when a jump is made from the first childapplication to the second child application; transferring, by the parentapplication, page data corresponding to the second child applicationidentifier to the second child application; generating, according to thepage data, a second child application page over the first childapplication page; and displaying the second child application page. 2.The method according to claim 1, wherein after the acquiring, by thefirst child application, a second child application identifiercorresponding to a second child application to be jumped to, the methodfurther comprises: acquiring a jump path used for recording one or moreexisting child application jumping relationships, the jump pathincluding one or more child application identifiers arranged in aspecific sequence based on one or more previous jumps; moving the secondchild application identifier to an end of the jump path when the secondchild application identifier exists in the jump path; and adding thesecond child application identifier to the end of the jump path when thesecond child application identifier does not exist in the jump path. 3.The method according to claim 2, further comprising: acquiring a returninstruction from the second child application; determining the secondchild application identifier in response to the return instruction;searching the jump path for a third child application identifier that isadjacent to the second child application identifier and is locatedbefore the second child application identifier; and returning to a thirdchild application page corresponding to the third child applicationidentifier.
 4. The method according to claim 3, wherein the returning toa third child application page corresponding to the third childapplication identifier comprises: when a third child applicationcorresponding to the third child application identifier is run by theparent application in a background state, returning to the third childapplication page corresponding to the third child application leftduring a corresponding previous jump; and when the third childapplication corresponding to the third child application identifier hasfinished running, returning to a default child application pagecorresponding to the third child application identifier.
 5. The methodaccording to claim 2, wherein the second child application comprises anative plug-in child application; and the moving the second childapplication identifier to the end of the jump path when the second childapplication identifier exists in the jump path comprises: when thesecond child application identifier exists in the jump path, determininga consecutive native plug-in child application identifier that isadjacent to the second child application identifier in the jump path andis located after the second child application identifier; and moving thesecond child application identifier to the end of the jump path, anddeleting the consecutive native plug-in child application identifier inthe jump path.
 6. The method according to claim 2, wherein the secondchild application is a third-party child application, and the methodfurther comprises: monitoring a close instruction by using the secondchild application; when a close instruction is detected and a firstnative plug-in child application identifier exists before a foremostthird-party child application identifier in the jump path, returning toa first native plug-in child application corresponding to the firstnative plug-in child application identifier; and when a closeinstruction is detected and the first native plug-in child applicationidentifier does not exist before the foremost third-party childapplication identifier in the jump path, returning to the parentapplication.
 7. The method according to claim 6, wherein the returningto a first native plug-in child application corresponding to the firstnative plug-in child application identifier comprises: when more thanone first native plug-in child application identifier exists before theforemost third-party child application identifier in the jump path,acquiring a second native plug-in child application identifier, whereinthe second native plug-in child application identifier is adjacent tothe first third-party child application identifier and is located beforethe first third-party child application identifier; determining a secondnative plug-in child application page, wherein the second native plug-inchild application page is a page corresponding to a second nativeplug-in child application corresponding to the second native plug-inchild application identifier during a jump; and displaying the secondnative plug-in child application page.
 8. The method according to claim1, wherein the transferring page data corresponding to the second childapplication identifier to the second child application comprises:switching to a parent application page used for triggering a childapplication jump, wherein the parent application page is a pagedisplayed by the parent application; triggering, by using the parentapplication page, acquisition of the page data corresponding to thesecond child application identifier; and transferring the page data tothe second child application.
 9. The method according to claim 1,wherein after the acquiring, by using the first child application, asecond child application identifier corresponding to a second childapplication to be jumped to, the method further comprises: acquiring afirst parent application page identifier corresponding to a switched-tofirst parent application page and a jump path used for recording one ormore existing child application jumping relationships, the jump pathincluding one or more child application identifiers arranged in aspecific sequence based on one or more previous jumps; when the acquiredsecond child application identifier exists in the jump path, deleting asecond parent application page identifier that is adjacent to the secondchild application identifier in the jump path and is located after thesecond child application identifier; adding the first parent applicationpage identifier to the end of the jump path; and moving the second childapplication identifier after the first parent application pageidentifier.
 10. An application processing apparatus, comprising aprocessor and a memory, the memory storing computer readableinstructions, and the instructions causing the processor to: display afirst child application page of a first child application, the firstchild application being run by a parent application; acquire, by usingthe first child application, a second child application identifiercorresponding to a second child application to be jumped to; run, by theparent application, the second child application when a jump is madefrom the first child application to the second child application;transfer, by the parent application, page data corresponding to thesecond child application identifier to the second child application;generate, according to the page data, a second child application pageover the first child application page; and display the second childapplication page.
 11. The apparatus according to claim 10, wherein thecomputer readable instructions may enable the processor to: acquire ajump path used for recording one or more existing child applicationjumping relationships, the jump path including one or more childapplication identifiers arranged in a specific sequence based on one ormore previous jumps; move the second child application identifier to anend of the jump path when the second child application identifier existsin the jump path; and add the second child application identifier to theend of the jump path when the second child application identifier doesnot exist in the jump path.
 12. The apparatus according to claim 11,wherein the computer readable instructions may enable the processor to:acquire a return instruction by using the second child application;determine the second child application identifier in response to thereturn instruction; search the jump path for a third child applicationidentifier that is adjacent to the second child application identifierand is located before the second child application identifier; andreturn to a third child application page corresponding to the thirdchild application identifier.
 13. The apparatus according to claim 12,wherein the computer readable instructions may enable the processor to:when a third child application corresponding to the third childapplication identifier is run by the parent application in a backgroundstate, return to the third child application page corresponding to thethird child application left during a corresponding previous jump; whenthe third child application corresponding to the third child applicationidentifier has finished running, return to a default child applicationpage corresponding to the third child application identifier.
 14. Theapparatus according to claim 11, wherein the child application comprisesa native plug-in child application, and the computer readableinstructions may enable the processor to: determine a consecutive nativeplug-in child application identifier that is adjacent to the secondchild application identifier in the jump path and is located after thesecond child application identifier when the second child applicationidentifier exists in the jump path; and move the second childapplication identifier to the end of the jump path, and delete theconsecutive native plug-in child application identifier in the jumppath.
 15. The apparatus according to claim 11, wherein the childapplication is a third-party child application, and the computerreadable instructions may enable the processor to: monitor a closeinstruction by using the second child application; when a closeinstruction is detected and a first native plug-in child applicationidentifier exists before a foremost third-party child applicationidentifier in the jump path, returning to a first native plug-in childapplication corresponding to the first native plug-in child applicationidentifier; and when a close instruction is detected and the firstnative plug-in child application identifier does not exist before theforemost third-party child application identifier in the jump path,return to the parent application.
 16. The apparatus according to claim15, wherein the computer readable instructions may enable the processorto: when more than one first native plug-in child application identifierexists before the foremost third-party child application identifier inthe jump path, acquire a second native plug-in child applicationidentifier, wherein the second native plug-in child applicationidentifier is adjacent to the first third-party child applicationidentifier and is located before the first third-party child applicationidentifier; determine a second native plug-in child application page,wherein the second native plug-in child application page is a pagecorresponding to a second native plug-in child application correspondingto the second native plug-in child application identifier during a jump;and display the second native plug-in child application page.
 17. Theapparatus according to claim 10, wherein the computer readableinstructions may enable the processor to: switch to a parent applicationpage used for triggering a child application jump, wherein the parentapplication page is a page displayed by the parent application; trigger,by using the parent application page, acquisition of the page datacorresponding to the second child application identifier; and transferthe page data to the second child application.
 18. The apparatusaccording to claim 10, wherein the computer readable instructions mayenable the processor to: acquire a first parent application pageidentifier corresponding to a switched-to first parent application pageand a jump path used for recording one or more existing childapplication jumping relationships, the jump path including one or morechild application identifiers arranged in a specific sequence based onone or more previous jumps; when the acquired second child applicationidentifier exists in the jump path, delete a second parent applicationpage identifier that is adjacent to the second child applicationidentifier in the jump path and is located after the second childapplication identifier; add the first parent application page identifierto the end of the jump path; and move the second child applicationidentifier after the first parent application page identifier.
 19. Anon-transitory computer readable storage medium storing computerreadable instructions, when being executed by a processor, the computerreadable instructions causing the processor to perform: displaying afirst child application page of a first child application, the firstchild application being run by a parent application; acquiring, by thefirst child application, a second child application identifiercorresponding to a second child application to be jumped to; running, bythe parent application, the second child application when a jump is madefrom the first child application to the second child application;transferring, by the parent application, page data corresponding to thesecond child application identifier to the second child application;generating, according to the page data, a second child application pageover the first child application page; and displaying the second childapplication page.
 20. The storage medium according to claim 19, whereinthe computer readable instructions further cause the processor toperform: after the acquiring, by the first child application, a secondchild application identifier corresponding to a second child applicationto be jumped to, acquiring a jump path used for recording one or moreexisting child application jumping relationships, the jump pathincluding one or more child application identifiers arranged in aspecific sequence based on one or more previous jumps; moving the secondchild application identifier to an end of the jump path when the secondchild application identifier exists in the jump path; and adding thesecond child application identifier to the end of the jump path when thesecond child application identifier does not exist in the jump path.